Release 10.1A: OpenEdge Deployment:
Managing 4GL Applications

Time stamp validation

For each table, OpenEdge maintains a time stamp indicating when the schema was last changed. When compiling a procedure, OpenEdge inserts the time stamp into the r-code for each database table accessed by the procedure. This time stamp is the value of the _Last-change field in the metaschema _File record for each table. Note that sequence changes have no effect on time stamp validation.

R-code execution with time stamps

When executing a procedure using time stamp validation, OpenEdge checks to make sure that the time stamps for all accessed tables match those contained in the r-code. If a time stamp does not match, the procedure does not execute.

To use time stamp validation, compile the procedure with each database connected using the Time Stamp (-tstamp) connection parameter. Otherwise, OpenEdge uses CRC validation.

Note: The Time Stamp (-tstamp) parameter is supported for backward compatibility only.